Understanding task persistence
Active Unisphere configuration tasks persist across a server shutdown and subsequent restart. Inactive configuration tasks do not persist.
When the SMAS server is restarted, it restores all persisted tasks in the task list (based on the user and the storage system).
The status of each restored task is determined by its status before the server shutdown, as detailed in the following table:
| Task status before server shutdown | Task status post server shutdown | ||
|---|---|---|---|
| Created | |||
|
Aborted Validated Running Successfully Run has error Prepare has error Submit has error Define has error Validate has error Done Failed |
|||
|
Prepare in progress Abort in progress Submitted Prepared Defined Pending NA Acquiring lock Lock acquire failed Running During run During preview |
Created | ||
| Commit in progress | Unknown
|
||
